CVE-2026-31618
fbdev: tdfxfb: avoid divide-by-zero on FBIOPUT_VSCREENINFO
Description
In the Linux kernel, the following vulnerability has been resolved: fbdev: tdfxfb: avoid divide-by-zero on FBIOPUT_VSCREENINFO Much like commit 19f953e74356 ("fbdev: fb_pm2fb: Avoid potential divide by zero error"), we also need to prevent that same crash from happening in the udlfb driver as it uses pixclock directly when dividing, which will crash.
INFO
Published Date :
April 24, 2026, 3:16 p.m.
Last Modified :
June 1, 2026, 5:16 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Update the Linux kernel to the latest version.
- Ensure the tdfxfb and udlfb drivers are updated.
- Apply relevant security patches for the kernel.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-31618.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-31618 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-31618
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-31618 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-31618 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 01, 2026
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/2f207e46c62688bb7eb4e3feaf9a0d94020fb0c9 Added Reference https://git.kernel.org/stable/c/59bde9e0930efef1286768cb65fc78d5e5267f93 Added Reference https://git.kernel.org/stable/c/6c05191598eca87a87329b3f6e4a0825775f09cf -
Initial Analysis by [email protected]
Apr. 28, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Added CWE CWE-369 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:2.6.12:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:2.6.12:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:2.6.12:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:2.6.12:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:2.6.12:-:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.24 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 6.19.14 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 7.0 up to (excluding) 7.0.1 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.83 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 2.6.12.1 up to (excluding) 6.6.136 Added Reference Type kernel.org: https://git.kernel.org/stable/c/53cb4e79a07124d2ebe502983c29800104080b47 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/63dfb0b4741f46d65b667c4275132b3d1966acc8 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/6567d3e1aaadfebf44ce7dc9ea2630323cd4c736 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/859a239d58a812b61267d9944b701affe6a6244e Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/8f98b81fe011e1879e6a7b1247e69e06a5e17af2 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/fc386daa6846551a88d338ba9864fc2812cd9030 Types: Patch -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Apr. 27, 2026
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/859a239d58a812b61267d9944b701affe6a6244e -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Apr. 27, 2026
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/8f98b81fe011e1879e6a7b1247e69e06a5e17af2 -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Apr. 24, 2026
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: fbdev: tdfxfb: avoid divide-by-zero on FBIOPUT_VSCREENINFO Much like commit 19f953e74356 ("fbdev: fb_pm2fb: Avoid potential divide by zero error"), we also need to prevent that same crash from happening in the udlfb driver as it uses pixclock directly when dividing, which will crash. Added Reference https://git.kernel.org/stable/c/53cb4e79a07124d2ebe502983c29800104080b47 Added Reference https://git.kernel.org/stable/c/63dfb0b4741f46d65b667c4275132b3d1966acc8 Added Reference https://git.kernel.org/stable/c/6567d3e1aaadfebf44ce7dc9ea2630323cd4c736 Added Reference https://git.kernel.org/stable/c/fc386daa6846551a88d338ba9864fc2812cd9030